System architecture matrix . reference

Cloudworkz OS . How the system works

Named map of every layer of the operating system: connectors that bring data in, skills that transform it, the vault that stores it, engines that run on schedule, and renders that present it back. With actual names, paths, and data flow.

5 layers + L3 deep dive 17 vault folders 25 canonical routes 24 skills inventoried 10 engines 11 MCP connectors 6 renders

The five layers

Data moves left to right. Connectors pull from outside systems; skills transform; the vault stores; engines reconcile in the background; renders present back to humans.

LAYER 1
Connectors
11 MCPs
LAYER 2
Skills
24 named
LAYER 3
Vault
17 folders
LAYER 4
Engines
10 scheduled
LAYER 5
Renders
5 live

Layer 1 . Connectors (MCPs)

External systems Claude can read from or write to. Each is a Model Context Protocol server with named tools.

ConnectorWhat it accessesKey named toolsStatus
Obsidian Vault (BenAI Relay) The vault itself. Authoritative store. Syncs to mobile + web + remote Claude clients. vault_read, vault_write, vault_append, vault_list, vault_search, vault_move, vault_delete, vault_folders, vault_relays live
Google Drive Google Drive files, Docs, Sheets. Gemini Notes Docs (auto-generated by Meet) live here. search_files, read_file_content, get_file_metadata, list_recent_files, create_file, copy_file, download_file_content, get_file_permissions live
Slack Team comms layer per Surface Decision V2. Audio notes + daily digests + async responses. slack_send_message, slack_read_channel, slack_read_thread, slack_search_public, slack_create_canvas, slack_schedule_message, slack_search_users, slack_list_channel_members live
Notion Team ops-side per Surface V2: kanban, calendar, task DBs, blockers, comments. Synced from vault. notion-create-pages, notion-update-page, notion-search, notion-fetch, notion-create-database, notion-create-view, notion-get-comments, notion-create-comment live
Fireflies AI meeting note-taker. Joins Google Meet calls, transcribes. Newly added (May 2026). fireflies_get_transcript, fireflies_get_summary, fireflies_search, fireflies_get_analytics, fireflies_create_soundbite, fireflies_get_active_meetings live
Gmail Email inbox. Drafts, labels, threads, search. search_threads, get_thread, create_draft, list_drafts, label_thread, label_message, create_label, list_labels live
Google Calendar Calendar events, scheduling, attendees. list_events, get_event, create_event, update_event, delete_event, suggest_time, respond_to_event, list_calendars live
Cowork The Cowork desktop app itself. Artefact persistence, file delete, folder selection. create_artifact, update_artifact, list_artifacts, read_widget_context, allow_cowork_file_delete, request_cowork_directory live
Claude in Chrome Browser automation. JS-rendered pages, form input, screenshots, network/console reading. navigate, get_page_text, computer, javascript_tool, form_input, read_console_messages, read_network_requests, find, browser_batch live
Scheduled Tasks Cron-style scheduler. Recurring or one-shot future Claude sessions independent of Mac state. create_scheduled_task, update_scheduled_task, list_scheduled_tasks live
MCP Registry Anthropic's connector registry. Discover and suggest MCPs Tom hasn't installed yet. search_mcp_registry, list_connectors, suggest_connectors live

Layer 2 . Skills

Three categories. Vault-internal skills live at Skills/{name}/ and fire via verbal trigger or canon-registered shortcut. External mirrors are symlinks into Skills/external/ from ~/.claude/skills/ per canon Rule 29. Plugin skills are loaded by Cowork at session start and appear in <available_skills>.

Vault-internal skills (canon-referenced, 8)

NamePathWhat it doesTrigger
transcript-ingest Skills/transcript-ingest/ 10-pass protocol: extract entities/decisions/framings/tasks/projects/considerations/context from a transcript and route into vault. intake this transcript
diagnose Skills/diagnose/ Disciplined diagnosis loop for bugs and performance regressions: reproduce, minimise, hypothesise, instrument, fix. diagnose this
grill-with-docs Skills/grill-with-docs/ Stress-test a plan against existing domain model + documented decisions; update CONTEXT.md inline. explicit call
handoff Skills/handoff/ Compact a conversation into a handoff doc for another agent. explicit call
internal-comms Skills/internal-comms/ House formats for internal comms: status reports, leadership updates, FAQs, incident reports. "write a status report" etc
karpathy-guidelines Skills/karpathy-guidelines/ Coding discipline: think before coding, simplicity, surgical changes, goal-driven execution. auto on code tasks
triage Skills/triage/ State machine for triaging incoming issues, bugs, feature requests; preps for AFK agent. "triage this"
vault-operator Skills/vault-operator/ Scheduled vault-operator profile prompt. Runs the OS on cadence per the operator schedule. scheduled task

External mirrored skills (Skills/external/, 16)

NameWhat it doesSource
boardroomBoardroom-style decision support (raise prep + investor conversations)cloudflare/boardroom_skills
brainstormingStructured idea generationexpert-skills
brand-discoverBrand voice discovery (read existing assets, infer voice)knowledge-work-plugins
brand-voice-enforcementApply brand voice rules to draftsknowledge-work-plugins
cavemanAdversarial review of LLM output (catches over-helpfulness)caveman repo
deep-researchMulti-step web research with structured outputclaude-deep-research-skill
dispatching-parallel-agentsOrchestrate multiple subagents on parallel tasksexpert-skills
expert-skillsMeta-skill containing the expert-skills suiteexpert-skills
grill-meAdversarial grilling of a proposal or plansuperpowers / pocock
handoff (mirror)External handoff skill (paired with vault handoff)expert-skills
premortemPre-mortem analysis: imagine the plan failed, work backwardspremortem repo
subagent-driven-developmentUse subagents to drive a development task end-to-endexpert-skills
to-prdConvert a rough brief into a PRDexpert-skills
verification-before-completionForce verification step before marking a task doneexpert-skills
writing-plansStructured plan-writing skillexpert-skills
zoom-outForce a step back from detail to see the larger frameexpert-skills

Plugin skills loaded this session

From <available_skills> at session start. Three plugin namespaces visible:

SkillWhat it doesTriggered by
anthropic-skills:docxCreate / read / edit Word docs (.docx)"word doc" or .docx mention
anthropic-skills:pptxSlide decks (.pptx) read and write"deck", "slides", "presentation"
anthropic-skills:xlsxSpreadsheets (.xlsx, .csv, .tsv) read and edit"spreadsheet", "excel"
anthropic-skills:pdfPDF read, write, merge, OCR, forms"PDF" or .pdf mention
anthropic-skills:canvas-designVisual art in PNG/PDF (posters, designs)"poster", "design"
anthropic-skills:web-artifacts-builderComplex Claude.ai HTML artefacts (React + Tailwind + shadcn)"artefact build"
anthropic-skills:internal-commsStatus reports, leadership updates, FAQs, incident reports"write a status report"
anthropic-skills:mcp-builderBuild MCP servers (Python FastMCP or Node/TypeScript)"build an MCP"
anthropic-skills:handoffCompact conversation into handoff doc"handoff to next session"
anthropic-skills:triageState machine for triaging issues"triage this"
anthropic-skills:skill-creatorCreate new skills, optimise descriptions, run evals"create a skill"
anthropic-skills:diagnoseBug + perf-regression diagnosis loop"diagnose this", "debug this"
anthropic-skills:karpathy-guidelinesCoding discipline rules (auto on code tasks)code tasks
anthropic-skills:setup-coworkGuided Cowork onboarding (plugins, connectors, skills)"set up Cowork"
anthropic-skills:consolidate-memoryMerge / prune memory files; fix stale facts"consolidate memory"
obsidian:os-mcpDeploy Relay MCP to Railway; give Claude vault access"set up the OS MCP"
obsidian:os-operatorBuild + schedule a personalized Operator prompt that runs the second-brain on cadence"operate my second brain"
obsidian:os-optimizerFramework-driven vault audit (9 frameworks F1-F9)"optimize vault"
obsidian:os-setupBootstrap BenAI OS vault structure + onboarding"set up", "bootstrap"
obsidian:team-osInstall BenAI Relay fork (RBAC + team-vault sharing)"set up team OS"

Layer 3 . Vault (17 Relay-shared folders)

The canonical store. Every piece of information has a designated home per the Knowledge Routing table in root CLAUDE.md. No catch-all; if routing is unclear, default to _scratch/ with route: pending.

FolderWhat lives hereOwner pattern
Context/Static-ish operating context: operator prefs, org info, strategy, ICP, pain-points, services, brand, infrastructure, stakeholders, team, market, benai-relaytom-king (canonical)
Intelligence/Meetings, decisions, competitors, market, processes, research, inbox. Time-stamped, immutable records.tom-king
Projects/Each named project gets a folder: Unlock, Cloudworkz-OS, Sales-Loop, Investor-Raise, Yachai, booker-hub-split, cloudworkz-hub, OS-Optimization-2026-Q2, EUK-Website, SafeSchool, Wolter, etc.per project
Team/Profiles: cloudworkz/Profiles/{name} for team, External/contractors/{name} for contractors. Each has Daily/, task-list/Tasks.md, Outbox/, sub-schedules/.per person
Atomic-System/Customer-facing component library, ships 11 June 2026.Claudia Chavez
Branding/Brand assets, design system, visual identity. Populate-first per 24 May decision.Claudia Chavez
BrainBox/Developed ideas as HTML presentations + source.md pairs. Per-slug folders.tom-king
Departments/Department charters, KPIs, SOPs per department.per department
Onboarding/Onboarding docs per role / per person.tom-king
Resources/Reusable content: frameworks, templates, engines, renders, proposed-canon-patches.tom-king
Skills/Vault-internal skills + external mirrors. Skill-specific reference material.tom-king
Daily/Org-level Daily/ (deprecated for canon writes; profile Daily/ is canonical).deprecated
_scratch/TTL-30d working artefacts; default routing for unclassified outputs (Rule 27).tom-king
CW — Command/, CW — Finance & Reporting/, CW — Marketing/, Live Artifact - Strategy and Team Clouds/Legacy reference. Read-only. Pre-migration canonical layer (3929 files combined).read-only

Layer 3 deep dive . Information types and the routing matrix

The folder list above tells you WHERE things go. The matrix below tells you WHAT goes where, WHO writes it, and HOW each information type is identified by its frontmatter type: value.

Reading order: the canonical routing table first (the contract for every information type), then generated outputs (what Claude produces in-session), then the sub-folder inventory inside each major folder (what's actually on disk), then the cross-cutting matrices (skills and engines mapped to routes), then three end-to-end lifecycles showing how the matrix is exercised in practice.

3a . The canonical knowledge routing table

From root CLAUDE.md § Knowledge Routing. Every named information type has exactly one home. No catch-all. If routing is unclear, default is _scratch/ with frontmatter route: pending per canon Rule 27.

Information typeCanonical routeOwner pattern
Operator preferences, style, habitsContext/operator.mdtom-king
Org structure, company info, productsContext/organization.mdtom-king
Strategy, OKRs, quarterly goalsContext/strategy.mdtom-king
Services, products, revenue linesContext/services.mdtom-king
ICP / customer profileContext/icp.mdtom-king
Customer + operator pain pointsContext/pain-points.mdtom-king
Tool stack, integrationsContext/infrastructure.mdtom-king
Brand voice, tone, messagingContext/brand.mdtom-king
Brand assets, design systemBranding/Claudia Chavez
Atomic system component libraryAtomic-System/Claudia Chavez
Developed ideas (HTML presentations)BrainBox/{slug}/tom-king
Vendor / partner / investor infoContext/stakeholders.mdtom-king
Team roster, agreementsContext/team.mdtom-king
Department info, charter, KPIsDepartments/{name}/per department
Person profile, daily notes, tasksTeam/cloudworkz/Profiles/{name}/that person
Contractor profileTeam/External/contractors/{name}/that contractor
Project info, briefs, retrosProjects/{name}/per project
Meetings, decisions, competitors, market, processes, research, audit-spawned itemsIntelligence/tom-king
Onboarding docsOnboarding/{name}.mdtom-king
Reusable frameworks, prompts, templates, engines, rendersResources/tom-king
Skill-specific referencesSkills/{skill-name}/tom-king
Tasks, action itemsactive profile's task-list/Tasks.mdthat profile
Personal daily noteactive profile's Daily/YYYY-MM-DD.mdthat profile
Canon user corrections.claude/rules/cloudworkz-canon.mdauto-loaded
Rules for assistant behaviourroot CLAUDE.mdtom-king

3b . Generated outputs (Claude-produced artefacts)

Same idea, narrower scope: what Claude produces in-session, where it lands, what type: frontmatter value identifies it. Every generated artefact carries type, project, owner, status, plus a your_move: line. No frontmatter, no save: default routing to _scratch/.

Generated artefactRoute totype: value
Draft to send (email, post, message)active profile's Outbox/draft
Report / memo for reviewDepartments/{name}/reports/ or Projects/{name}/reports/report
Research briefIntelligence/research/research
Meeting notesIntelligence/meetings/meeting
Decision recordIntelligence/decisions/decision
Idea presentation (developed)BrainBox/{slug}/brainbox-entry
Idea draft (uncommitted)BrainBox/_drafts/{slug}.mdbrainbox-draft
Working memo / scratch_scratch/ (TTL 30 days)scratch
Task spawned by outputactive profile's task-list/Tasks.md (entry, not file)n/a (Obsidian-task format)
Render (hosted HTML)Resources/renders/{name}/render
Folder indexthat folder's CLAUDE.mdfolder-claude

3c . What lives inside each major folder

Drill-down into the sub-folders + file inventory inside each top-level vault folder. This is the second resolution layer below the 17-folder list above.

Intelligence/ (7 sub-folders)

Sub-folderInformation typeFilename patternWritten by
meetings/Meeting notes (source of record for any meeting)YYYY-MM-DD-{slug}.mdtranscript-ingest skill
decisions/Decision records, immutable. Wikilink trail for supersession.YYYY-MM-DD-{slug}-V{n}.mdtranscript-ingest Pass 2/2b or manual
research/Research briefs, frameworks-in-development, V-numbered investigationsYYYY-MM-DD-{slug}-V{n}.mdmanual deep-research or transcript Pass 5
competitors/Per-competitor intel, signals, threat assessment{competitor-slug}.mdtranscript Pass 5c or manual
market/Market intel (Tom's market signals, trends, sector data){market-slug}.mdtranscript Pass 5c or manual
processes/Cross-cutting process docs (org-wide, not department SOPs){process-slug}.mdmanual
inbox/Audit-spawned items (CHECK-* files), Slack-ingest landings, Whisper transcriptions, untriaged signalsCHECK-YYYY-MM-DD-*.md, mixeddaily-audit, slack-ingest, manual
considerations/ (lazy-created)Options being weighed without resolution. Distinct from open questions and decisions. Created on first need by transcript-ingest Pass 5b.YYYY-MM-DD-{slug}.mdtranscript-ingest Pass 5b

Context/ (12 named files at folder root; no sub-folders)

FileWhat it holds
operator.mdTom's preferences, style rules, working habits
organization.mdCloudworkz/Unlock org structure, product hierarchy
strategy.mdOKRs, strategic anchors (Unlock 1 Oct 2026, raise April 2027, OS Oct 2027), dated strategy updates
services.mdCloudworkz services + revenue lines (Unlock, OS, Atomic-System, Yachay, etc.)
icp.mdIdeal customer profile (UK HNW segment, P-codes x engines)
pain-points.mdCustomer pain points + operator/internal pain points (Tom-as-bottleneck, etc.)
infrastructure.mdTool stack: Cowork, BenAI Relay, Supabase, Cloudflare, Notion, Drive, Slack, Fireflies
brand.mdVoice rules, tone, canonical CLOUDZ definition (per canon Rule 9c)
stakeholders.mdInvestors, advisors (Tony Vine-Lott), partners, vendors
team.mdTeam roster (canonical names per canon Rule 9), reporting lines
market.mdMarket context (segments, sizing, sector dynamics)
benai-relay.mdBenAI Relay sync architecture reference, State A/B/C semantics

Projects/ (16 active workstream folders)

Per-project layout: each Projects/{Name}/ folder contains README.md (project orientation), CLAUDE.md (folder-claude frontmatter + folder conventions), optionally brief-V{n}.md, reports/, retros/, _archive/. Active projects on disk:

ProjectWorkstreamStatus / ship
Unlock/UK HNW decision-support platform (subscription)ships 1 Oct 2026
Cloudworkz-OS/Operating layer powering Unlockcommercialises Oct 2027
Investor-Raise/£6.5M raise first closeApril 2027
Sales-Loop/Tom-owned sales loop (daily activate)activated 2026-05-25
OS-Optimization-2026-Q2/Audit-pass + Phase-2 prep for the OS itselfongoing
Team-Surface/Four-surface architecture build (HTML + Notion + Slack + vault)in flight
Team-Rollout/Team rollout for vault + Notion + Slack architecturein flight
EUK-Website/EUK website workstreamin flight
SafeSchool/SafeSchool engagement (legal context per canon Rule 7)in flight
Wolter/Wolter matter (instructed counsel)in flight
Yachai/Claudia Chavez sales / video / luxury-villa portfolioongoing
booker-hub-split/Booker hub split workstream (Marie booker context)in flight
cloudworkz-hub/Cross-device workstation prototypebrief-V1 queued
Roose-Design-Signoff/Roose design signoff workstreamin flight
Unlock-Content-Brain/Unlock content brain workstreamin flight
Unlock-Lead-Gen-Scripts/Unlock lead-gen script suitein flight

Team/cloudworkz/Profiles/{name}/ (per-person container)

Sub-pathWhat lives here
{Name}.mdThe person's profile (role, scope, context)
Daily/YYYY-MM-DD.mdPer-day notes (canonical Daily; not root Daily/)
task-list/Tasks.mdCanonical tasks for that person (Rule 22 split-path canon)
Outbox/Drafts to send: emails, posts, messages
sub-schedules/Per-person schedule notes (1-1s, recurring)
payslips/Payslip + comp records (tom-king only)

Resources/ (8 sub-folders)

Sub-folderWhat lives here
frameworks/Reusable frameworks, V-numbered briefs (bos-ecosystem-V1, sync-resilience-brief-V1, etc.)
engines/Scheduled background processes (see Layer 4)
renders/Hosted HTML renders (see Layer 5)
templates/Reusable file templates (meeting notes, decision records, project briefs)
principles/Operating principles, canonical statements
companies/Per-company reference dossiers
proposed-canon-patches/Queued canon proposals during V32 freeze (adoption resumes 2026-06-01)
_archive/Archived Resources material (retired engines, deprecated renders)

BrainBox/ (developed ideas, established 2026-05-26)

Sub-pathWhat lives here
CLAUDE.mdFolder index + full shortcut specs for "prepare for brainbox" and "add to brainbox"
_template/Clone-from-here template (index.html + source.md)
_drafts/{slug}.mdPrepared but uncommitted drafts (held until "add to brainbox" fires)
{idea-slug}/One committed idea per folder: index.html + source.md + optional assets/

3d . Skill x Route matrix (who writes where)

For each vault-internal skill or canon-registered shortcut, the routes it writes to. Read this as: "if I fire X, what gets touched."

Skill or shortcutTriggerRoutes written
transcript-ingest intake this transcript Intelligence/meetings/ (source-of-record), Intelligence/decisions/ (Pass 2/2b), Intelligence/considerations/ (Pass 5b, lazy-created), Intelligence/research/ (Pass 5 stubs), Intelligence/competitors/ + Intelligence/market/ (Pass 5c), Context/strategy.md + Context/pain-points.md + Context/team.md + Context/services.md + Context/brand.md (Pass 5c appends), Projects/{name}/ (Pass 4 project-state), profile task-list/Tasks.md (Pass 4 owner-actions), profile Daily/ (chain mentions)
"prepare for brainbox" prepare for brainbox BrainBox/_drafts/{slug}.md only (no commit; awaits "add to brainbox")
"add to brainbox" add to brainbox BrainBox/{slug}/index.html + BrainBox/{slug}/source.md, appends Active ideas table in BrainBox/CLAUDE.md, deletes draft from BrainBox/_drafts/ if applicable
"signing off" signing off Cowork artefact tom-king-signing-off (refresh), profile task-list/Tasks.md (Rule 21 close), 3-line chat reply
"clean up" clean up No vault writes (chat-only code-block readout + dashboard reorder suggestion)
diagnose diagnose this No vault writes by default; user routes the diagnosis output (typically Intelligence/research/ for the brief, profile Tasks.md for the fix)
internal-comms "write a status report" etc Profile Outbox/ (drafts) or Departments/{name}/reports/
triage triage this Relevant project's task-list or _scratch/ (state-machine output)
handoff explicit _scratch/handoff-{slug}.md or session-specific
karpathy-guidelines auto on code tasks No vault writes (behavioural rule; shapes how code edits happen)
grill-with-docs explicit Updates the target's CONTEXT.md inline; produces Intelligence/decisions/ ADRs when calls land
vault-operator scheduled task Per its prompt: Intelligence/inbox/ for findings, profile Tasks.md for queued items, profile Daily/ for the operator report

3e . Engine x Route matrix (background reads + writes)

For each engine, what it reads from and what it writes to. Engines run on launchd cadence per sync_all.sh orchestrator.

EngineReads fromWrites to
daily-auditWhole vault (10 checks: canon, frontmatter, sync state, engine health, em-dash drift, inventory)Intelligence/inbox/CHECK-YYYY-MM-DD-*.md
daily-log-writerProfile task-list/Tasks.md (any task moved to Done with today's date)Profile Daily/YYYY-MM-DD.md ("Completed today" append)
em-dash-auditWhole active vault (Rule 1 enforcement scan)tom-king Daily/ (drift report)
master-tasks-htmlProfile task-list/Tasks.mdExternal: master-tasks-tom.pages.dev (legacy, superseded by daily-triage artefact per Rule 21 V33)
notion-decisions-syncIntelligence/decisions/External: Notion decisions DB (idempotent via content hash)
notion-tasks-syncProfile task-list/Tasks.md AND per-person Notion kanbanNotion kanban (push); profile Tasks.md (pull for ticks; Rule 22 split-path)
os-dreamingWhole vault (reflective pass for structural debt + name corrections)Profile task-list/Tasks.md (audit-spawned tasks per Rule 24)
slack-ingestSlack channels + DM threads (Whisper transcription for audio)Intelligence/inbox/ (raw landings before triage)
team-htmlVault state (tasks by owner, project status, blockers)External: team-surface.pages.dev
sync_all.shOrchestrator; runs every engine in orderNo own writes; triggers each engine on the 15-min launchd cycle

3f . Three information lifecycles (how the matrix is exercised)

The matrices above are static. These three lifecycles show information moving through layers across time.

Lifecycle 1 . A decision (from meeting to Notion)

  1. Meeting happens (Google Meet); Fireflies joins or Gemini auto-Notes the call.
  2. Transcript fetched via fireflies_get_transcript or Drive search_files. Skill auto-fires.
  3. Pass 2 extracts the decision, Pass 2b traces the debate arc end-to-end (rejected alternatives become considerations).
  4. Pass 7 routing ledger proposes a row writing to Intelligence/decisions/YYYY-MM-DD-{slug}-V1.md with supersedes: wikilink to prior decisions if any.
  5. Pass 8 Confirm gate: nothing writes until Tom replies apply.
  6. Pass 9 writes the decision file with dual-write per Rule 15 V21.
  7. notion-decisions-sync engine picks up the new file within 15 min; pushes to Notion decisions DB via content hash.
  8. Downstream: superseded decisions get a back-wikilink trail. Any task spawned by the decision lands in profile Tasks.md, which notion-tasks-sync then propagates to the per-person Notion kanban.

Lifecycle 2 . A task (from creation to closure across surfaces)

  1. Task created either by transcript-ingest Pass 4 (extracted owner-action) or manually in chat or via signing off shortcut at session close.
  2. Written to canonical store: active profile's task-list/Tasks.md with Rule 20 scoring (urgency emoji + e: + i: + imp:).
  3. notion-tasks-sync pushes to per-person Notion kanban view (Rule 22 split-path: Tom in HTML artefact, team in Notion).
  4. Tick happens either in the daily-triage Cowork artefact (Tom) or in the Notion kanban (team member). Either tick lands at the canonical Tasks.md eventually.
  5. daily-log-writer engine sees the task moved to Done with today's date; appends "Completed today" to profile's Daily/YYYY-MM-DD.md.
  6. team-html engine rebuilds team-surface.pages.dev (every 15 min) so team-facing counts update.
  7. Rule 21 session-close: Claude updates Tasks.md and reports delta in chat; the daily-triage artefact reads live via vault_read on next open (no snapshot rebuild per Rule 21 V33).

Lifecycle 3 . An idea (from spark to BrainBox to Project)

  1. Source material: a chat, a folder, a file, or a pasted brief that contains the idea seed.
  2. "prepare for brainbox" fires; Claude reads the source, synthesises Challenge + Blueprint + Linked files + Status + Open questions + Next move; writes draft to BrainBox/_drafts/{slug}.md with type: brainbox-draft.
  3. Tom reviews the draft in chat (or edits the draft file directly). Re-prepare or kill if synthesis is wrong.
  4. "add to brainbox" commits: scaffolds BrainBox/{slug}/ with index.html + source.md from the template; appends Active ideas table in BrainBox/CLAUDE.md; deletes the draft.
  5. Idea matures: source.md is the source-of-truth; index.html regenerates from it as the idea evolves. status: moves seed → developing → parked or promoted.
  6. Promotion (when ready): idea moves to Projects/{name}/ with a new project README; the BrainBox entry gets a promoted_to: frontmatter line pointing to the project. BrainBox entry stays as the originating thinking record.

Layer 4 . Engines (scheduled background processes)

Live at Resources/engines/. Triggered by sync_all.sh on a launchd 15-minute cycle or by individual launchd plists. Each engine reads from the vault, transforms, writes back or to a render target.

EngineWhat it doesCadenceI/O
daily-auditDaily system audit: 10 checks covering canon compliance, frontmatter, sync state, engine health, em-dash drift, inventory.daily 06:00 BSTvault → Intelligence/inbox/CHECK-YYYY-MM-DD-*.md
daily-log-writerFor every task moved to Done with today's date, appends "Completed today" entry to profile's Daily/ note.every 15 minTasks.md → profile Daily/
em-dash-auditScans active vault for em-dash drift (Rule 1 enforcement). Reports counts in Daily.dailyvault → tom-king Daily/
master-tasks-htmlRebuilds hosted master-tasks page from Tasks.md. Now superseded by daily-triage Cowork artefact (Rule 21 V33).every 15 minTasks.md → master-tasks-tom.pages.dev (legacy)
notion-decisions-syncPushes Intelligence/decisions/ files to Notion decisions DB. Idempotent via content hash.every 15 minvault → Notion
notion-tasks-syncBidirectional sync between profile Tasks.md and per-person Notion kanban (Rule 22 split-path architecture).every 15 minvault ↔ Notion
os-dreamingReflective pass: spots audit-spawned tasks, name corrections, structural debt; queues to Tasks.md per Rule 24.nightlyvault → Tasks.md (audit-spawned)
slack-ingestPulls Slack audio notes + text threads into Intelligence/inbox/ via Whisper transcription.every 15 minSlack → Intelligence/inbox/
team-htmlRebuilds team-surface.pages.dev from vault data (tasks by owner, project status, blockers).every 15 minvault → team-surface.pages.dev
sync_all.shMaster orchestrator. Runs every engine in order. Single entrypoint.every 15 min via launchdorchestrator

Layer 5 . Renders (HTML outputs)

Hosted HTML pages built from vault data on schedule, presenting state in shapes markdown can't (dashboards, kanban with WIP limits, capacity bars, status boards, calculators, indexes). Audience varies per render.

RenderAudienceUse-momentPath
cloudworkz-hubTom personalCross-device workstation prototype (cloudworkz-hub V1 brief still queued)Resources/renders/cloudworkz-hub/
cw-welcome-onboardingTeam-facingWelcome / onboarding (migration to hosted HTML pending per audit cw-artefact-audit-4)Resources/renders/cw-welcome-onboarding/
transcript-ingest-explainerTom personalReference: what is the transcript-ingest skill, what's built, doc indexResources/renders/transcript-ingest-explainer/
werner-handover-briefWernerOS-layer handover brief, seven decisions for WernerResources/renders/werner-handover-brief/
werner-supabase-os-blueprintWerner / TomSupabase OS blueprint single-file renderResources/renders/werner-supabase-os-blueprint.html
cloudworkz-os-matrix (this page)Tom personalSystem architecture matrix: what skills, what routes, how it worksResources/renders/cloudworkz-os-matrix/

Plus: Cowork artefacts (Tom-personal, in-app)

Live in Cowork's artefact store, not the vault. Per artefact-registry.md:

ArtefactPurposeStatus
tom-king-daily-triageLive-read vault_read on open. Today / This week / Blocked. Replaces master-tasks per Rule 21 V33.live
tom-king-signing-offEnd-of-day boilerdown artefact (4 blocks: Done today / Left / Anchor check / Housekeeping). Fires via "signing off" shortcut.live
vault-read-probe-v1Diagnostic probe artefact, reports N open tasks via vault_read. Live-read pattern proof.live
unlock-booker-hub, cloudworkz-os-cockpitAudit-flagged for migration (cw-artefact-audit-5) or refresh (audit-6).in audit

How it works . worked example: a transcript lands

The most common operating cycle. A meeting happens; the OS turns it into structured vault state and presents it back. Named tools at each step.

  1. Layer 1 input: Google Meet records the call. Fireflies joins as a note-taker (or Gemini auto-generates "Notes by Gemini" Docs in Drive). The transcript lands at fireflies_get_transcript or as a Drive Doc reachable via search_files.
  2. Layer 2 skill fires: The transcript-ingest skill triggers automatically on Fireflies fetch, or you say intake this transcript. Pass 0 primes context via vault_read against active workstreams, team roster, recent decisions, recent meetings.
  3. Layer 2 extraction: Passes 1-6 extract entities, decisions (with 2b debate-arc tracking), framings, tasks + project-state, open questions, considerations, context updates, then Pass 6 orchestrator catches chains.
  4. Layer 2 routing ledger: Pass 7 produces a multi-target table naming every artefact + append the skill proposes. Pass 8 confirm gate waits for the appropriate reviewer (default active profile, reassignable).
  5. Layer 3 vault writes: Pass 9 dual-writes (per Rule 15 V21): meeting note to Intelligence/meetings/, decisions to Intelligence/decisions/, project notes to Projects/{name}/, considerations to Intelligence/considerations/ (lazy-created) or in-note, pain points to Context/pain-points.md, strategy updates to Context/strategy.md, research stubs to Intelligence/research/, tasks to active profile's task-list/Tasks.md.
  6. Layer 4 engines reconcile: Next launchd cycle (within 15 min), notion-decisions-sync pushes the new decisions to Notion. notion-tasks-sync pushes the new tasks to the per-person kanban. daily-log-writer appends to Daily/ if anything ticked off. team-html rebuilds the team page.
  7. Layer 5 renders update: tom-king-daily-triage Cowork artefact reads the updated Tasks.md live on next open. The team sees the new state at team-surface.pages.dev. Decisions are searchable in Notion. The meeting note is wikilinked from every derivative.

Total wall-clock from "meeting ends" to "structured state across all surfaces": about 20 minutes (transcript-ingest run + Pass 8 confirm + engines cycle). Without the skill, the same content takes hours and loses the chain.

Canon (the rules layer)

Behavioural rules that apply to every save. Lives at .claude/rules/cloudworkz-canon.md, auto-loaded every session via paths: ['**/*.md'] frontmatter. Current V33 (26 May 2026).

RuleWhat it enforces
Rule 0Task Intake protocol: 5-line block before any TaskCreate (Goal / Acceptance / Capabilities / Estimate / Open questions)
Rule 1No em-dashes. Substitute with period or comma at save-time
Rule 2No files in vault root. Every file lives in an existing folder per routing
Rule 3status + 2+ tags in frontmatter for every content note
Rule 4Wikilinks for every entity (people, projects, departments, concepts)
Rule 9, 9a, 9b, 9cCanonical names + roles: Marie BOOKER not Roberts, Fiorella Marketing Ops not Director, Tony ADVISOR not legal, Claudia Chavez owns Yachay (not Lambourne), CLOUDZ definition
Rule 15 V21Dual-write: every Relay-shared write is vault_write then local Write, identical content, vault_read first if not yet read this session
Rule 16Code work follows karpathy-guidelines
Rule 17Surgical by default. Don't fix adjacent rot during a content edit
Rule 18Per-step verify-checks for multi-step work
Rule 19Relay sync-recovery: BenAI Relay toggle (off, 3s, on) clears State C
Rule 20Task scoring schema: 4 dimensions (urgency emoji + e: + i: + imp:)
Rule 21 V33Session-close discipline: update Tasks.md + report delta in chat. Step 2 (artefact rebuild) retired in V33
Rule 22Split-path tick architecture: Tom in HTML artefact, team in Notion kanban, Tasks.md canonical
Rule 23Scheduled tasks use MCP only (cloud-resident), never local-mount tools
Rule 24Audit-action contract: audits queue tasks, not just report
Rule 26Session-handoff artefact (queued for retire/ratify decision)
Rule 27Mandatory shared-folder routing. Unclassified outputs default to _scratch/ with route: pending
Rule 28Paste-and-run Terminal commands preferred when feasible
Rule 29Skills/external/ namespace for Cowork mirrors of ~/.claude/skills/
Rule 30Don't swap the Obsidian Relay plugin without an ADR
Rule 31Never write secrets into paste-and-run shell commands
Rule 32Relay-state stamp on audit measurements
Rule 33Manifest verification at write-close (structural trigger, closed verb list)

Verbal shortcuts (canon-registered triggers)

Phrases you say that fire defined protocols. Live in root CLAUDE.md § Shortcuts.

TriggerWhat it firesSpec location
"signing off"End-of-day boilerdown. 3-line chat headline + Cowork artefact tom-king-signing-off with 4 blocks (Done / Left / Anchor / Housekeeping)canon § Shortcuts
"clean up"Mid-session re-anchor. 6-line code-block readout (Goal / Where / Open / Drift / Debt / Next move) plus Dashboard reorder suggestioncanon § Shortcuts
"intake this transcript"Ten-pass transcript-ingest skill (Pass 0 prime + Passes 1-9). Variants: process / ingest / fan this out. Auto-fires on Fireflies fetchSKILL.md V3.1

Where to find what . cheat sheet

Quick reference for "I need X, where does it live".

I want to find / write...Look at / route to
A past meetingIntelligence/meetings/YYYY-MM-DD-{slug}.md
A decision someone madeIntelligence/decisions/YYYY-MM-DD-{slug}-V{n}.md
A research briefIntelligence/research/YYYY-MM-DD-{slug}-V{n}.md
A person's profile + their tasks + their daily notesTeam/cloudworkz/Profiles/{slug}/ or Team/External/contractors/{slug}/
My tasksTeam/cloudworkz/Profiles/tom-king/task-list/Tasks.md
Today's Daily noteTeam/cloudworkz/Profiles/tom-king/Daily/YYYY-MM-DD.md
Strategy / OKRsContext/strategy.md
Customer pain pointsContext/pain-points.md
Tool stackContext/infrastructure.md
Brand voice rulesContext/brand.md + canon Rule 9c
An active projectProjects/{Name}/README.md
A reusable framework or templateResources/frameworks/{slug}-V{n}.md
A skill's specSkills/{slug}/SKILL.md or anthropic-skills:* in <available_skills>
A rule of behaviour.claude/rules/cloudworkz-canon.md (auto-loaded)
A folder conventionthat folder's CLAUDE.md
A hosted HTML viewResources/renders/{name}/index.html
A scratch / work-in-progress note_scratch/ (TTL 30 days)